Unauthorized tracking device detection and prevention

ABSTRACT

The detection and prevention of unauthorized tracking devices is described herein. For example, a mobile device may be configured to detect nearby wireless devices. The communication signal between a detected wireless device and the mobile device may be tracked over time, and used to programmatically determine the likelihood that the detected wireless device is an unknown tracking device. The user of the mobile device may be given a notification and related data when a suspicious device is identified, and the user may choose to identify the unknown tracking device as an authorized tracking device or an unauthorized tracking device. When a detected wireless device is identified as an unauthorized tracking device, various remedial actions may be performed by a user and/or a central tracking system. In one example, the central tracking system remotely deactivates the unauthorized tracking device.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/389,092, filed Dec. 22, 2016, which is incorporated by reference inits entirety.

BACKGROUND

This disclosure relates generally to tracking devices, and morespecifically, to preserving a user's data security and privacy in atracking device environment.

Electronic tracking devices track the location of people and/or objects.For example, a user can use GPS technology to track a device remotelyand determine a location of a user of the device. In another example, auser can attach a tracking device to an important object, such as keysor a wallet, and use the features of the tracking device to more quicklylocate the object, (e.g., if it becomes lost).

However, tracking devices and corresponding systems suffer from one ormore disadvantages. If a tracking device is attached to a possession ofa user without the user's permission, location and/or movement of theuser can be tracked without authorization from the user. Accordingly,there is a need to prevent the unauthorized tracking of the user in suchcircumstances, thereby protecting the privacy of the user.

SUMMARY

Techniques for detecting and preventing unauthorized tracking devicesare discussed herein. For example, a mobile device may be configured todetect nearby wireless devices. The presence of a wireless device may betracked by a mobile device based on communications detected from thewireless device over time, and can be used to programmatically determinethe likelihood that the nearby wireless device is an unauthorizedtracking device. The user of the mobile device may be given anotification and related data when a suspicious device is identified,and the user may choose to register the device for authorization, orflag the device as unauthorized. When a wireless device is identified asan unauthorized tracking device, various remedial actions may beperformed by the user and/or a remote tracking system. In one example,the tracking system is configured to remotely deactivate theunauthorized tracking device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example tracking system environment in which atracking device can operate, according to one embodiment.

FIG. 2 illustrates an example tracking system for use in a trackingsystem environment, according to one embodiment.

FIG. 3 illustrates an example user mobile device for use in a trackingsystem environment, according to one embodiment.

FIG. 4 illustrates an example community mobile device for use in atracking system environment, according to one embodiment.

FIG. 5 illustrates an example tracking device for use in a trackingsystem environment, according to one embodiment.

FIG. 6 illustrates an example tracking system environment includingunauthorized devices, according to one embodiment.

FIG. 7 illustrates a process for managing unauthorized tracking devices,according to one embodiment.

FIG. 8 illustrates a process for identifying an unauthorized trackingdevice, according to one embodiment.

The figures depict various embodiments of the present invention forpurposes of illustration only. One skilled in the art will readilyrecognize from the following discussion that alternative embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles of the invention described herein.

DETAILED DESCRIPTION

Environment Overview

Embodiments described herein detail functionality associated with atracking device. A user can attach a tracking device to or enclose thetracking device within an object, such as a wallet, keys, a car, a bike,a pet, or any other object that the user wants to track. The user canthen use a mobile device (e.g., by way of a software applicationinstalled on the mobile device) or other device or service to track thetracking device and corresponding object. For example, the mobile devicecan perform a local search for a tracking device attached to a near-byobject. However, in situations where the user is unable to locate thetracking device using their own mobile device (e.g., if the trackingdevice is beyond a distance within which the mobile device and thetracking device can communicate), the user can leverage the capabilitiesof a community of users of a tracking device system.

In particular, a tracking system (also referred to herein as a “cloudserver” or simply “server”) can maintain user profiles associated with aplurality of users of the tracking device system. The tracking systemcan associate each user within the system with one or more trackingdevices associated the user (e.g., tracking devices that the user haspurchased and is using to track objects owned by the user). If theuser's object becomes lost or stolen, the user can send an indicationthat the tracking device is lost to the tracking system, which is incommunication with one or more mobile devices associated with thecommunity of users in communication with the system. The tracking systemcan set a flag indicating the tracking device is lost. When one of acommunity of mobile devices that are scanning for nearby trackingdevices and providing updated locations to the tracking systemidentifies a flagged tracking device, the tracking system can associatethe received location with the flagged tracking device, and relay thelocation to a user of the tracking device, thereby enabling the user tolocate the lost tracking device.

FIG. 1 illustrates an example tracking system environment in which atracking device can operate, according to one embodiment. Theenvironment of FIG. 1 includes a tracking system 100 communicativelycoupled to a mobile device 102 associated with the user 103 via a firstnetwork 108. The tracking system 100 is also communicatively coupled toa plurality of community mobile devices 104 a through 104 n(collectively referred to herein as “community mobile devices 104”)associated with a plurality of users 105 a through 105 n of the trackingsystem 100 (collectively referred to herein as “community users 105”)via the first network 108. As will be explained in more detail below,the tracking system 100 can allow the user 103 to manage and/or locate atracking device 106 associated with the user 103. In some embodiments,the tracking system 100 leverages the capabilities of community mobiledevices 104 to locate the tracking device 106 if the location of thetracking device is unknown to the user 103 and beyond the capabilitiesof mobile device 102 to track. In some configurations, the user 103 mayown and register multiple tracking devices 106. Although FIG. 1illustrates a particular arrangement of the tracking system 100, mobiledevice 102, community mobile devices 104, and tracking device 106,various additional arrangements are possible.

In some configurations, the user 103 may be part of the community ofusers 105. Further, one or more users 105 may own and register one ormore tracking devices 106. Thus, any one of the users within thecommunity of users 105 can communicate with tracking system 100 andleverage the capabilities of the community of users 105 in addition tothe user 103 to locate a tracking device 106 that has been lost.

The tracking system 100, mobile device 102, and plurality of communitymobile devices 104 may communicate using any communication platforms andtechnologies suitable for transporting data and/or communicationsignals, including known communication technologies, devices, media, andprotocols supportive of remote data communications.

In certain embodiments, the tracking system 100, mobile device 102, andcommunity mobile devices 104 may communicate via a network 108, whichmay include one or more networks, including, but not limited to,wireless networks (e.g., wireless communication networks), mobiletelephone networks (e.g., cellular telephone networks), closedcommunication networks, open communication networks, satellite networks,navigation networks, broadband networks, narrowband networks, theInternet, local area networks, and any other networks capable ofcarrying data and/or communications signals between the tracking system100, mobile device 102, and community mobile devices 104. The mobiledevice 102 and community of mobile devices 104 may also be incommunication with a tracking device 106 via a second network 110. Thesecond network 110 may be a similar or different type of network as thefirst network 108. In some embodiments, the second network 110 comprisesa wireless network with a limited communication range, such as aBluetooth or Bluetooth Low Energy (BLE) wireless network. In someconfigurations, the second network 110 is a point-to-point networkincluding the tracking device 106 and one or more mobile devices thatfall within a proximity of the tracking device 106. In such embodiments,the mobile device 102 and community mobile devices 104 may only be ableto communicate with the tracking device 106 if they are within a closeproximity to the tracking device, though in other embodiments, thetracking device can use long-distance communication functionality (forinstance, a GSM transceiver) to communicate with either a mobile device102/104 or the tracking system 100 at any distance. In someconfigurations, the mobile device 102 and one or more community mobiledevices 104 may each be associated with multiple tracking devicesassociated with various users.

As mentioned above, FIG. 1 illustrates the mobile device 102 associatedwith the user 103. The mobile device 102 can be configured to performone or more functions described herein with respect to locating trackingdevices (e.g., tracking device 106). For example, the mobile device 102can receive input from the user 103 representative of information aboutthe user 103 and information about a tracking device 106. The mobiledevice 102 may then provide the received user information, trackingdevice information, and/or information about the mobile device 102 tothe tracking system 100. Accordingly, the tracking system 100 is able toassociate the mobile device 102, the user 103, and/or the trackingdevice 106 with one another. In some embodiments, the mobile device 102can communicate with the tracking device 106 and provide informationregarding the location of the tracking device to the user 103. Forexample, the mobile device 102 can detect a communication signal fromthe tracking device 106 (e.g., by way of second network 110) as well asa strength of the communication signal or other measure of proximity todetermine an approximate distance between the mobile device 102 and thetracking device 106. The mobile device 102 can then provide thisinformation to the user 103 (e.g., by way of one or more graphical userinterfaces) to assist the user 103 to locate the tracking device 106.Accordingly, the user 103 can use the mobile device 102 to track andlocate the tracking device 106 and a corresponding object associatedwith the tracking device 106. If the mobile device 102 is located beyondthe immediate range of communication with the tracking device 106 (e.g.,beyond the second network 110), the mobile device 102 can be configuredto send an indication that a tracking device 106 is lost to the trackingsystem 100, requesting assistance in finding the tracking device. Themobile device 102 can send an indication of a lost device in response toa command from the user 103. For example, once the user 103 hasdetermined that the tracking device 106 is lost, the user can provideuser input to the mobile device 102 (e.g., by way of a graphical userinterface), requesting that the mobile device 102 send an indicationthat the tracking device 106 is lost to the tracking system 100. In someexamples, the lost indication can include information identifying theuser 103 (e.g., name, username, authentication information), informationassociated with the mobile device 102 (e.g., a mobile phone number),information associated with the tracking device (e.g., a unique trackingdevice identifier), or a location of the user (e.g., a GPS location ofthe mobile device 102 at the time the request is sent).

The tracking system 100 can be configured to provide a number offeatures and services associated with the tracking and management of aplurality of tracking devices and/or users associated with the trackingdevices. For example, the tracking system 100 can manage informationand/or user profiles associated with user 103 and community users 105.In particular, the tracking system 100 can manage information associatedwith the tracking device 106 and/or other tracking devices associatedwith the user 103 and/or the community users 105.

As mentioned above, the tracking system 100 can receive an indicationthat the tracking device 106 is lost from the mobile device 102. Thetracking system 100 can then process the indication in order to help theuser 103 find the tracking device 106. For example, the tracking system100 can leverage the capabilities of the community mobile devices 104 tohelp find the tracking device 106. In particular, the tracking system100 may set a flag for a tracking device 106 to indicate that thetracking device 106 lost and monitor communications received from thecommunity mobile devices 104 indicating the location of one or moretracking devices 106 within proximity of the community mobile devices104. The tracking system 100 can determine whether a specific locationis associated with the lost tracking device 106 and provide any locationupdates associated with the tracking device 106 to the mobile device102. In one example, the tracking system may receive constant updates oftracking device 106 locations regardless of whether a tracking device106 is lost and provide a most recent updated location of the trackingdevice 106 in response to receiving an indication that the trackingdevice 106 is lost.

In some configurations, the tracking system 100 can send a locationrequest associated with the tracking device 106 to each of the communitymobile devices 104. The location request can include any instructionsand/or information necessary for the community mobile devices 106 tofind the tracking device 102. For example, the location request caninclude a unique identifier associated with the tracking device 106 thatcan be used by the community mobile devices 104 to identify the trackingdevice 106. Accordingly, if one of the community mobile devices 104detects a communication from the tracking device 106 (e.g., if thecommunity mobile device 104 is within range or moves within range of thecommunication capabilities of the tracking device 106 and receives acommunication signal from the tracking device 106 including orassociated with the unique identifier associated with the trackingdevice 106), the community mobile device 104 can inform the trackingsystem 100. Using the information received from the community mobiledevices 104, the tracking system 100 can inform the user (e.g., by wayof the mobile device 102) of a potential location of the tracking device106.

As shown in FIG. 1 and as mentioned above, the tracking system 100 cancommunicate with a plurality of community mobile devices 104 associatedwith corresponding community users 105. For example, an implementationmay include a first community mobile device 104 a associated with afirst community user 105 a, a second community mobile device 104 bassociated with a second community user 105 b, and additionalcommunication mobile devices associated with additional community usersup to an nth community mobile device 104 n associated with an nthcommunity user 105 n. The community mobile devices 104 may also includefunctionality that enables each community mobile device 104 to identifya tracking device 106 within a proximity or communicable range of thecommunity mobile device 104. In one example, a first community mobiledevice 104 a within proximity of a tracking device 106 can communicatewith the tracking device 106, identify the tracking device 106 (e.g.,using a unique identifier associated with the tracking device 106),and/or detect a location associated with the tracking device 106 (e.g.,a location of the first mobile community device 104 a at the time of thecommunication with the tracking device 106). This information can beused to provide updated locations and/or respond to a location requestfrom the tracking system 100 regarding the tracking device 106. In someembodiments, the steps performed by the first community mobile device104 a can be hidden from the first community user 105 a. Accordingly,the first community mobile device 104 a can assist in locating thetracking device 106 without bother and without the knowledge of thefirst community user 105 a.

As mentioned above, the tracking system 100 can assist a user 103 inlocating a tracking device 106. The tracking device may be a chip, tile,tag, or other device for housing circuitry and that may be attached toor enclosed within an object such as a wallet, keys, purse, car, orother object that the user 103 may track. Additionally, the trackingdevice 106 may include a speaker for emitting a sound and/or atransmitter for broadcasting a beacon. In one configuration, thetracking device 106 may periodically transmit a beacon signal that maybe detected using a nearby mobile device 102 and/or community mobiledevice 104. In some configurations, the tracking device 106 broadcasts abeacon at regular intervals (e.g., one second intervals) that may bedetected from a nearby mobile device (e.g., community mobile device104). The strength of the signal emitted from the tracking device 106may be used to determine a degree of proximity to the mobile device 102or community mobile device 104 that detects the signal. For example, ahigher strength signal would indicate a close proximity between thetracking device 106 and the mobile device 102 and a lower strengthsignal would indicate a more remote proximity between the trackingdevice 106 and the mobile device 102, though in some embodiments, thetracking device 106 can intentionally vary the transmission strength ofthe beacon signal. In some cases, the strength of signal or absence of asignal may be used to indicate that a tracking device 106 is lost.

System Overview

FIG. 2 illustrates an example tracking system for use in a trackingsystem environment, according to one embodiment. As shown, the trackingsystem 100 may include, but is not limited to, an association manager204, a tracking device location manager 206, a data manager 208, and anunauthorized tracking device manager, each of which may be incommunication with one another using any suitable communicationtechnologies. It will be recognized that although managers 204-208 areshown to be separate in FIG. 2, any of the managers 204-208 may becombined into fewer managers, such as into a single manager, or dividedinto more managers as may serve a particular embodiment.

The association manager 204 may be configured to receive, transmit,obtain, and/or update information about a user 103 and/or informationabout one or more specific tracking devices (e.g., tracking device 106).In some configurations, the association manager 204 may associateinformation associated with a user 103 with information associated witha tracking device 106. For example, user information and trackinginformation may be obtained by way of a mobile device 102, and theassociation manager 204 may be used to link the user information andtracking information. The association between user 103 and trackingdevice 106 may be used for authentication purposes, or for storing userinformation, tracking device information, permissions, or otherinformation about a user 103 and/or tracking device 106 in a database.

In some embodiments, the association manager 204 may be used tofacilitate identification of authorized and unauthorized devices fromone or more wireless devices connected with the mobile device 102. Forexample, the association manager 204 may be configured to accessauthorized device identifiers defining a set of authorized devices. Theauthorized devices may define authorized tracking devices, such as ownertracking devices associated with the user of the mobile device, sharedtracking devices associated with a connected user of the user of themobile device, or other authorized (e.g., non-tracking) wireless devices(e.g., a peripheral device). Each authorized devices may be associatedwith a device identifier. A detected wireless device that fails toinclude an authorized device identifier may be identified as anunauthorized device. In some embodiments, a list of unauthorized deviceidentifiers may also be stored and referenced to determine whetherdetected wireless device is an authorized or unauthorized device.

The tracking system 100 also includes a tracking device location manager206. The tracking device location manager 206 may receive and process anindication that the tracking device 106 is lost from a mobile device(e.g., mobile device 102 or community mobile devices 104). For example,the tracking system 100 may receive a lost indication from a mobiledevice 102 indicating that the tracking device 106 is lost. The trackingdevice location manager 206 may set a flag on a database (e.g., trackerdatabase 212) indicating that the tracking device 106 is lost. Thetracking device location manager 206 may also query a database todetermine tracking information corresponding to the associated user 103and/or tracking device 106. The tracking system 100 may obtain trackingdevice information and provide the tracking device information or otherinformation associated with the tracking device 106 to a plurality ofcommunity mobile devices 104 to be on alert for the lost or unavailabletracking device 106.

The tracking device location manager 206 may also receive a locationfrom one or more community mobile devices 104 that detect the trackingdevice 106, for instance in response to the community mobile devicereceiving a beacon signal transmitted by the tracking device 106,without the tracking device 106 having been previously marked as lost.In such embodiments, a user corresponding to the mobile device 102 canrequest a most recent location associated with the tracking device fromthe tracking system 100, and the location manager 206 can provide thelocation received from the community mobile device for display by themobile device 102. In some embodiments, the location manager 206provides the location of the tracking device 106 received from acommunity mobile device either automatically (for instance if thetracking device 106 is marked as lost) or at the request of a user ofthe mobile device 102 (for instance, via an application on the mobiledevice 102). The location manager 206 can provide a location of atracking device 106 to a mobile device 102 via a text message, pushnotification, application notification, automated voice message, or anyother suitable form of communication.

The tracking device location manager 206 may further manage providingindications about whether a tracking device 106 is lost or not lost. Forexample, as discussed above, the tracking device location manager 206may provide a location request to the community of mobile devices 104indicating that a tracking device 106 is lost. Additionally, uponlocation of the tracking device 106 by the user 103 or by one of thecommunity of users 105, the tracking device location manager 206 mayprovide an indication to the user 103, community user 105, or trackingsystem 100 that the tracking device 106 has been found, thus removingany flags associated with a tracking device and/or canceling anylocation request previously provided to the community of users 105. Forexample, where a user 103 sends an indication that the tracking device106 is lost to the tracking system 100 and later finds the trackingdevice 106, the mobile device 102 may provide an indication to thetracking system 100 that the tracking device 106 has been found. Inresponse, the tracking device location manager 206 may remove a flagindicating that the tracking device 106 is lost and/or provide anupdated indication to the community of users 105 that the trackingdevice 106 has been found, thus canceling any instructions associatedwith the previously provided location request. In some configurations,the notification that the tracking device 106 has been found may beprovided automatically upon the mobile device 102 detecting the trackingdevice 106 within a proximity of the mobile device 102. Alternatively,the notification that the tracking device 106 has been found may beprovided by the user 103 via user input on the mobile device 102. Inanother example, a known user (e.g., a friend or family member) withwhom the tracking device 106 has been shared may provide an indicationthat the tracking device 106 has been found.

The tracking system 100 additionally includes a data manager 208. Thedata manager 208 may store and manage information associated with users,mobile devices, tracking devices, permissions, location requests, andother data that may be stored and/or maintained in a database related toperforming location services of tracking devices. As shown, the datamanager 208 may include, but is not limited to, a user database 210, atracker database 212, permissions data 214, and location request data216. It will be recognized that although databases and data within thedata manager 208 are shown to be separate in FIG. 2, any of the userdatabase 210, tracker database 212, permissions data 214, and locationrequest data 216 may be combined in a single database or manager, ordivided into more databases or managers as may serve a particularembodiment.

The data manager 208 may include the user database 210. The userdatabase 210 may be used to store data related to various users. Forexample, the user database 210 may include data about the user 103 aswell as data about each user 105 in a community of users 105. Thecommunity of users 105 may include any user that has provided userinformation to the tracking system 100 via a mobile device 102, 104 orother electronic device. The user information may be associated with oneor more respective tracking devices 106, or may be stored without anassociation to a particular tracking device. For example, a communityuser 105 may provide user information and permit performance of trackingfunctions on the community mobile device 104 without owning or beingassociated with a tracking device 106. The user database 210 may alsoinclude information about one or more mobile devices or other electronicdevices associated with a particular user.

The user database 210 may also include information defining sharedtracking devices. A shared tracking device refers to a tracking devicethat is owned by a different user, but is an authorized device fortracking the user. For example, the user database 210 may associate theuser with another user (e.g., a friend, connection, etc.) such that atracking device owned by the other is identified as a shared trackingdevice for the user.

The data manager 208 may also include a tracker database 212. Thetracker database 212 may be used to store data related to trackingdevices. For example, the tracker database 212 may include tracking datafor any tracking device 106 that has been registered or otherwiseauthorized with the tracking system 100. Tracking data may includeunique tracker identifications (IDs) or “device identifiers” associatedwith individual tracking devices 106. Tracker IDs may be associated witha respective user 103. Tracker IDs may also be associated with multipleusers. Additionally, the tracker database 212 may include any flags orother indications associated with whether a specific tracking device 106has been indicated as lost and whether any incoming communications withregard to that tracking device 106 should be processed based on thepresence of a flag associated with the tracking device 106. In someembodiments, the tracker database 212 may further include an authorizedtracking device flag indicating whether a specific tracking device 106has been identified as an unauthorized tracking device for a user.

The data manager 208 may further include permissions data 214 andlocation request data 216. Permissions data 214 may include levels ofpermissions associated with a particular user 103 and/or tracking device106. For example, permissions data 214 may include additional users thathave been indicated as sharing a tracking device 106, or who have beengiven permission to locate or receive a location of a tracking device106. Location request data 216 may include information related to alocation request or a lost indication received from the user 103 via amobile device 102.

The tracking system 100 further includes an unauthorized device manager218. The unauthorized device manager 218 may be configured to performthe functionalities discussed herein with respect to identifyingunauthorized tracking devices from wireless devices detected by a mobiledevice 102, and performing suitable remedial actions. The unauthorizeddevice manager 218 may be further configured to remotely disable anauthorized tracking device if possible, such as when the unauthorizedtracking device is a tracking device managed by the tracking system 100(or a “managed tracking device,” as used herein). In another example, ifthe unauthorized tracking device is not a managed tracking device orotherwise cannot be controlled by the tracking system 100, then anotification may be sent to a (e.g., third party) system associated withthe unauthorized tracking device.

FIG. 3 illustrates an example user mobile device for use in a trackingsystem environment, according to one embodiment. As shown, the mobiledevice 102 may include, but is not limited to, a user interface manager302, a location request manager 304, a database manager 306, and atracking manager 308, each of which may be in communication with oneanother using any suitable communication technologies. It will berecognized that although managers 302-308 are shown to be separate inFIG. 3, any of the managers 302-308 may be combined into fewer managers,such as into a single manager, or divided into more managers as mayserve a particular embodiment.

As will be explained in more detail below, the mobile device 102includes the user interface manager 302. The user interface manager 302may facilitate providing the user 103 access to data on a trackingsystem 100 and/or providing data to the tracking system 100. Further,the user interface manager 302 provides a user interface by which theuser 103 may communicate with tracking system 100 and/or tracking device106 via mobile device 102.

The mobile device 102 may also include a location request manager 304.The location request manager 304 may receive and process a request inputto the mobile device 102 to send an indication that a tracking device106 is lost to a tracking system 100. For example, the user 103 mayprovide an indication that a tracking device 106 is lost, unreachable,or otherwise unavailable from the mobile device 102 via the userinterface manager 302, and the location request manager 304 may processthe lost indication and provide any necessary data to the trackingsystem 100 for processing and relaying a location request to other users105 over a network 108. In some configurations, an indication that atracking device 106 is lost is provided via user input. Alternatively,the indication may be transmitted automatically in response to themobile device 102 determining that a tracking device 106 is lost.

In addition, the location request manager 304 can request a location ofthe tracking device 106 without the tracking device 106 being identifiedas lost. For instance, a user can access a tracking device locationfeature of an application running on the mobile device 102 (for example,via the user interface manager 302), and the location request manager304 can request a most recent location of the tracking device 106 fromthe tracking system 100. The location request manager 304 can receivethe most recent location from the tracking system 100, and can displaythe most recent location via the user interface manager 302.

The mobile device 102 may also include a database manager 306. Thedatabase manager 306 may maintain data related to the user 103, trackingdevice 106, permissions, or other data that may be used for locating atracking device 106 and/or providing a request to a tracking system 100for locating one or more tracking devices 106 associated with the user103. Further, the database manager 306 may maintain any information thatmay be accessed using any other manager on the mobile device 102.

The mobile device 102 may further include a tracking manager 308. Thetracking manager 308 may also a tracking application (e.g., a softwareapplication) for communicating with and locating a tracking device 106associated with the user 103. The tracking manager 308 may be configuredto communicate with the unauthorized tracking device manager 218 of thetracking system 100 to provide the functionality discussed herein withrespect to unauthorized device detection and handling. For example, thetracking manager 308 may be configured to receive notificationsregarding unauthorized devices, and facilitate user definition ofauthorized devices.

The tracking manager 308 may be one configuration of a trackingapplication installed on the mobile device 102 that provides thefunctionality for locating a tracking device 106 and/or requestinglocation of a tracking device 106 using a tracking system 100 and/or aplurality of community mobile devices 104. As shown, the trackingmanager 308 may include, but is not limited to, a Bluetooth Low Energy(BLE) manager 310, a persistence manager 312, a local files manager 314,a motion manager 316, a secure storage manager 318, a settings manager320, a location manager 322, a network manager 324, a notificationmanager 326, a sound manager 328, a friends manager 330, a photo manager332, an authentication manager 334, and a device manager 336. Thus, thetracking manager 308 may perform any of the functions associated withmanagers 310-338, described in additional detail below.

The BLE manager 310 may be used to manage communication with one or moretracking devices 106. The persistence manager 312 may be used to storelogical schema information that is relevant to the tracking manager 308.The local files manager 314 may be responsible for managing all filesthat are input or output from the mobile device 102. The motion manager316 may be responsible for all motion management required by thetracking manager 308. The secure storage manager may be responsible forstorage of secure data, including information such as passwords andprivate data that would be accessed through this sub-system. Thesettings manager 320 may be responsible for managing settings used bythe tracking manager 308. Such settings may be user controlled (e.g.,user settings) or defined by the tracking manager 308 for internal use(e.g., application settings) by a mobile device 102 and/or the trackingsystem 100. The location manager 322 may be responsible for locationtracking done by the tracking manager 308. For example, the locationmanager 322 may manage access to the location services of the mobiledevice 102 and works in conjunction with other managers to persist data.The network manager 324 may be responsible for all Internetcommunications from the tracking manager 308. For example, the networkmanager 324 may mediate all Internet API calls for the tracking manager308. The notification manager 326 may be responsible for managing localand push notifications required by the tracking manager 308. The soundmanager 328 may be responsible for playback of audio cues by thetracking manager 308. The friends manager 330 may be responsible formanaging access to contacts and the user's social graph. The photomanager 332 may be responsible for capturing and managing photos used bythe tracking manager 308. The authentication manager 334 may beresponsible for handling the authentication (e.g., sign in or login) ofusers. The authentication manager 334 may also include registration(e.g., sign up) functionality. The authentication manager 334 furthercoordinates with other managers to achieve registration functionality.The device manager 336 may be responsible for managing the devicesdiscovered by the tracking manager 308. The device manager 336 mayfurther store and/or maintain the logic for algorithms related to devicediscovery and update.

FIG. 4 illustrates an example community mobile device for use in atracking system environment, according to one embodiment. As shown, thecommunity mobile device 104 may include, but is not limited to, a userinterface manager 402, a tracking device manager 404, a database manager406, and a tracking manager 408, each of which may be in communicationwith one another using any suitable communication technologies. The userinterface manager 402, database manager 406, and tracking manager 408illustrated in FIG. 4 may include similar features and functionality asthe user interface manager 302, database manager 306, and trackingmanager 308 described above in connection with FIG. 3. It will berecognized that although managers 402-408 are shown to be separate inFIG. 4, any of the managers 402-408 may be combined into fewer managers,such as into a single manager, or divided into more managers as mayserve a particular embodiment.

The community mobile device 104 may include a tracking device manager404. The tracking device manager 404 may facilitate scanning for nearbytracking devices 106. In some configurations, the tracking devicemanager 404 can continuously or periodically scan (e.g., once persecond) for nearby tracking devices 106. The tracking device manager 404may determine whether to provide an updated location of the nearbytracking device 106 to the tracking system 100. In some configurations,the tracking device manager 404 provides a location of a nearby trackingdevice 106 automatically. Alternatively, the tracking device manager 404may determine whether the location of the tracking device 106 has beenrecently updated, and may determine whether to provide an updatedlocation based on the last time a location of the tracking device 106has been updated (e.g., by the community mobile device 104). Forexample, where the community mobile device 104 has provided a recentupdate of the location of a tracking device 106, the tracking devicemanager 404 may decide to wait a predetermined period of time (e.g., 5minutes) before providing an updated location of the same trackingdevice 106.

In one configuration, the tracking device manager 404 may receive andprocess a location request or other information relayed to the communitymobile device 104 by the tracking system 100. For example, the trackingdevice manager 404 may receive an indication of a tracking device 106that has been indicated as lost, and provide a location of the trackingdevice 106 if it comes within proximity of the community mobile device104. In some configurations, the community mobile device 104 isconstantly scanning nearby areas to determine if there is a trackingdevice 106 within a proximity of the community mobile device 104.Therefore, where a tracking device 106 that matches information providedby the tracking system 100 (e.g., from the location request) comeswithin proximity of the community mobile device 104, the tracking devicemanager 404 may generate and transmit a response to the location requestto the tracking system 100, which may be provided to the user 103associated with the tracking device 106. Further, generating andtransmitting the response to the tracking request may be conditioned onthe status of the tracking device 106 being flagged as lost by themobile device 102 and/or the tracking system 100.

The tracking device manager 404 may additionally provide otherinformation to the tracking system 100 in response to receiving thetracking request. For example, in addition to providing a location ofthe community mobile device 104, the tracking device manager may providea signal strength associated with the location to indicate a level ofproximity to the location of the community mobile device 104 provided tothe user 103. For example, if a signal strength of a communicationsignal is high, the location provided to the user 103 is likely to bemore accurate than a location accompanied by a low signal strength. Thismay provide additional information that the user 103 may find useful indetermining the precise location of tracking device 106.

As described above, the tracking device manager 404 may determinewhether to send a location within the proximity of the tracking device106 to the tracking system 100. The determination of whether to send alocation to the tracking system 100 may be based on a variety offactors. For example, a tracking device manager 404 may determine tosend a location of the tracking device 106 to a tracking system 100based on whether the detected tracking device 106 has been indicated aslost or if a tracking request has been provided to the community mobiledevice 104 for the particular tracking device 106. In someconfigurations, the community mobile device 104 may send an update of alocation of a tracking device 106 even if the tracking device 106 is notassociated with a current tracking request or if the tracking device 106is not indicated as lost. For example, where the location of a trackingdevice 106 has not been updated for a predetermined period of time, thecommunity mobile device 104 may provide an update of a tracking devicelocation to the tracking system 100, regardless of whether a trackingrequest has been received.

In some configurations, the community mobile device 104 may includeadditional features. For example, the community mobile device 104 mayallow a tracking system 100 to snap and download a photo using photofunctionality of the community mobile device 104. In someconfigurations, this may be an opt-in feature by which a community user105 permits a tracking system 100 to take a snap-shot and possiblyprovide a visual image of an area within a proximity of the trackingdevice 106.

FIG. 5 illustrates an example tracking device for use in a trackingsystem environment, according to one embodiment. The tracking device 106of FIG. 5 includes an interface 502, a transceiver 504, a controller506, one or more sensors 508, and a GPS unit 510. The transceiver 504 isa hardware circuit capable of both transmitting and receiving signals.It should be noted that in other embodiments, the tracking device 106includes fewer, additional, or different components than thoseillustrated in FIG. 5.

The interface 502 provides a communicative interface between thetracking device 106 and one or more other devices, such as a mobiledevice 102. For instance, the interface 502 can instruct the transceiver504 to output beacon signals as described above (for example,periodically or in response to a triggering event, such as a detectedmovement of the tracking device 106). The interface 502 can, in responseto the receiving of signals by the transceiver 504 from, for instance,the mobile device 102, manage a pairing protocol to establish acommunicative connection between the tracking device 106 and the mobiledevice 102. As noted above, the pairing protocol can be a BLEconnection, though in other embodiments, the interface 502 can manageother suitable wireless connection protocols (such as WiFi, GlobalSystem for Mobile Communications or GSM, and the like).

The controller 506 is a hardware chip that configures the trackingdevice 106 to perform one or more functions or to operate in one oroperating modes or states. For instance, the controller 506 canconfigure the interval at which the transceiver broadcasts beaconsignals, can authorize or prevent particular devices from pairing withthe tracking device 106 based on information received from the devicesand permissions stored at the tracking device, can increase or decreasethe transmission strength of signals broadcasted by the transceiver, canconfigure the interface to emit a ringtone or flash an LED light, canenable or disable various tracking device sensors, can enable or disablea tracking device GPS unit, can enable or disable communicativefunctionality of the tracking device 106 (such as a GSM transmitter andreceiving), can configure the tracking device into a sleep mode or awakemode, can configure the tracking device into a power saving mode, andthe like. The controller 506 can configure the tracking device toperform functions or to operate in a particular operating mode based oninformation or signals received from a device paired with or attemptingto pair with the tracking device 106, based on an operating state orconnection state of the tracking device 106, based on user-selectedsettings, based on information stored at the tracking device 106, basedon a detected location of the tracking device 106, based on historicalbehavior of the tracking device 106 (such as a previous length of timethe tracking device was configured to operate in a particular mode),based on information received from the sensors 508 or the GPS 510, orbased on any other suitable criteria.

In some embodiments, the controller 506 may be configured to facilitateremote activation or deactivation of the tracking device 105, such asbased on received instructions from the tracking system 100. Thetracking system 100 may be configured to communicate activation ordeactivation instructions to the tracking device 105 via the mobiledevice 102. For example, the instruction may be generated by thetracking system 100 when an unauthorized device is identified as anunauthorized tracking device managed by the tracking system 100, thensent to the mobile device 102 via the first network 108, and then to thetracking device 106 via the second network 110. In another example, theinstruction may be provided to the tracking device 106 via a communitymobile device 104. In another example, the instruction may be providedto the tracking device 106 without traveling through a mobile device102/104, such as directly through the first network 108.

The sensors 508 can include motion sensors (such as gyroscopes oraccelerators), altimeters, orientation sensors, proximity sensors, lightsensors, or any other suitable sensor configured to detect anenvironment of the tracking device 106, a state of the tracking device106, a movement or location of the tracking device 106, and the like.The sensors 508 are configured to provide information detected by thesensors to the controller 506. The GPS unit 510 is configured to detecta location of the tracking device 106 based on received GPS signals, andis configured to provide detected locations to the controller 506.

Privacy Preservation in a Tracking Device Environment

In some embodiments, a tracking system environment may be configured tofacilitate unauthorized tracking device management, includingunauthorized tracking device detection and remote handling.

FIG. 6 illustrates an example tracking system environment includingunauthorized devices, according to one embodiment. The environment inFIG. 6 is a local environment of the user 103 carrying the mobile device102, including the second network 110 and one or more wireless devicesconnected with the mobile device 102 via the second network 110.

As discussed above, the second network 110 may include a wirelessnetwork with a limited communication range, such as a Bluetooth orBluetooth Low Energy (BLE) wireless network. In one example, the secondnetwork 110 is a BLE wireless network having a communication range ofapproximately 10 meters from the mobile device 102. The second network110 may include other types of suitable personal area networks capableof wireless communication at a limited communication range such thatcommunication with a wireless device indicates location proximitybetween the wireless device and the mobile device 102.

The wireless devices connected with the mobile device 102 may includeone or more unauthorized devices 602 and one or more authorized devices604. When an unknown device is detected by the mobile device 102 via thesecond network, the unknown device may be classified into one of theclasses of devices 602-614. Examples of an unauthorized device 602 mayinclude an unauthorized tracking device 606 or other unauthorized(non-tracking) wireless device 608. An authorized device 604 may includean owner tracking device 610, a shared tracking device 612, or otherauthorized (non-tracking) wireless device 614.

The unauthorized tracking device 608 refers to a tracking device whichmay be managed by the tracking system 100 (e.g., a “managed trackingdevice,” as used herein), or alternatively, a tracking device managed orassociated with a separate system. The unauthorized device 608 refers toa wireless device that is not authorized by the user 103, but has notbeen identified as a tracking device (e.g., connection qualitiesindicate low tracking device probability) or has been identified asbeing a device different from a tracking device (e.g., nearby mobiledevice of another user).

The owner tracking device 610 refers to a tracking device owned by theuser 103. For example, the user 103 may have registered the ownertracking device 610 with the tracking system 100 as the owner or managerof the owner tracking device 610. The shared tracking device 612 refersto a tracking device owned by another user. The shared tracking device612 may be associated with the user 103, such as based on the owner ofthe shared tracking device 612 being a connected user of the user 103.The authorized wireless device 614 refers to a non-tracking device thatis authorized by the user 103.

In some embodiments, authorized devices may be stored to facilitatedevice identification. For example, each authorized device may beassociated with a unique device identifier that is stored at thetracking system 100 (e.g., at tracker database 212). The mobile device102 may be configured to scan, listen for, or otherwise detect wirelessdevices within the communicable range of the mobile device 102. In someembodiments, unique identifiers associated with known unauthorizeddevices may additionally or alternatively be stored to facilitate deviceidentification.

As discussed above in connection with FIG. 1, the mobile device 102 isconnected with the tracking system 100 via the first network 108. Thewireless devices 602/604 are connected with the mobile device 102 viathe second network 110. Thus, the mobile device 102 may serve asintermediary for communications between a tracking device 106 and thetracking system 100 (e.g., even when the tracking device 106 supportsonly short range wireless communication). In some embodiments, thetracking system 100 may be configured to remotely control trackingdevices 106, such as the activation or deactivation of managed trackingdevices, based on sending an instruction to the tracking devices 106.The instruction may be provided directly to the tracking device orthrough the mobile device 102, such as via the first network 108, themobile device 102, the second network 110, and then to the trackingdevice 106.

FIG. 7 illustrates a process 700 for managing unauthorized trackingdevices, according to one embodiment. Process 700 may be performedwithin the tracking system environments shown in FIGS. 1 and 6 to enablea user to detect and prevent unauthorized tracking devices. Process 700is primarily discussed with respect to a central system configuration,where an unauthorized tracking device manager 218 of the tracking system100 is configured to perform remote management of tracking devices 106for a mobile device 102. However, in a local configuration, some or allof the functionality may be performed by the tracking manager 308 of themobile device 102.

At 710, the mobile device 106 may be configured to detect wirelessdevices within a communication range of the mobile device 106. Themobile device 102 may be configured to scan, listen for, or otherwisedetect wireless devices within the communicable range of the mobiledevice 102 using the second network 110. The wireless devices mayinclude unauthorized devices, authorized devices, or unknown deviceswithout a classification. Some of the wireless devices, whetherauthorized or unauthorized, may be tracking devices.

The mobile device 102 and the wireless devices may be configured totransfer communication signals. In some embodiments, a communicationsignal may include a device identifier or other unique identifierassociated with the wireless device. If the wireless device is atracking device 106, the tracking device 106 may store the deviceidentifier in a memory, and broadcast the device identifier to nearbymobile devices 102 (e.g., as a beacon at regular intervals). The mobiledevice 102 may be configured to receive the device identifiers ofconnected wireless devices, and transmit the device identifiers to thetracking system 100.

At 720, the tracking system 100 (e.g., the unauthorized tracking devicemanager 218) may be configured to identify an unauthorized trackingdevice from the detected wireless devices. Identification of anunauthorized tracking device may include determining, from the pool ofdetected wireless devices, a wireless device that is both unauthorizedand exhibiting communication signal or connection characteristics thatindicate the wireless device is tracking the user. The identificationmay be based on user input (e.g., device authorization based onregistration) and/or programmatic analysis of communication signalsbetween the mobile device 102 and the detected wireless devices.Although various techniques may be used to identify unauthorizedtracking devices from unknown wireless devices, an example process 800is discussed below in connection with FIG. 8.

At 730, the tracking system 100 may be configured to determine whetherthe unauthorized tracking device is a managed tracking device of thetracking system 100. A managed tracking device refers to a trackingdevice 106 that is controlled by the tracking system 100. The trackingsystem 100 may store a managed tracking device list including uniquedevice IDs for managed tracking devices. The device ID of anunauthorized tracking device may be compared with the device IDs ofmanaged tracking devices to determine whether the unauthorized trackingdevice is a managed tracking device.

In response to determining that the unauthorized tracking device is amanaged tracking device, process 700 may proceed to 740, where thetracking system 100 may be configured to remotely deactivate the managedtracking device. After a managed tracking device has been identified,the tracking system 100 may attempt to remotely control the managedtracking device if possible. For example, the tracking device 106 may beconfigured to provide a security token, password, key or other code thatis recognized by the tracking device 106, and causes the tracking device106 to function in accordance with instructions sent from the trackingsystem 100.

For an unauthorized tracking device 606 managed by the tracking system100, the instruction may define a remote deactivation command thatprevents the unauthorized tracking device 606 from wirelesslycommunicating with, listening to, or detecting the mobile device 102.Thus the tracking functionality of the unauthorized tracking device 606is disabled. Remote commands are not necessarily limited todeactivation. In another example, an instruction may define a remoteactivation command that enables wireless communication for the trackingdevice. Deactivation may refer to powering down the tracking device, ordeactivation of wireless communication components (e.g., transmitter,receiver, etc.) of the tracking device. In another example, deactivationmay include unregistering the unauthorized tracking device 606 for theowner, deactivating mobile device location detection/sharing for theunauthorized tracking device 606, disassociating the unauthorizedtracking device 606 with the user profile of the owner, orterminating/suspending the user profile or account of the owner, etc.

In some embodiments, remotely deactivating the managed tracking devicemay include sending the instruction to the managed tracking device viathe mobile device 102. For example, the tracking system 100 may beconfigured to control the tracking device 106 via the network 108, themobile device 102, the second network 110, and then the tracking device106.

In some embodiments, remotely deactivating the managed tracking devicemay include sending the instruction to the managed tracking device via acommunity mobile device 104 separate from the mobile device 102. Forexample, the tracking system 100 may be configured to control thetracking device 106 by communicating with the community mobile device104 via the first network 108, and the community mobile device 104 maycommunicate with the tracking device 106 via the first network 108, themobile device 102, the second network 110, and then the tracking device106. For example, the community device 104 may own or be associated withthe tracking device 106, and may be used to provide a security code orthe like to deactivate the tracking device 106.

In some embodiments, the control instructions and/or othercommunications between the tracking system 100 and the tracking device106 does not pass through any mobile device 102. For example, thetracking device 106 may directly connect with the tracking system 100via first network 108.

Returning to 730, in response to determining that the unauthorizedtracking device is not a managed tracking device, process 700 mayproceed to 750, where the tracking system 100 may be configured to senda notification to a system associated with the unauthorized trackingdevice. The notification may include a message indicating that theunauthorized tracking device has been identified for tracking the user103 without authorization, which may trigger remedial action by thesystem. In some embodiments, the notification may include a request todeactivate to unauthorized tracking device. Method 700 may be repeatedto provide tracking device identification and handling for wirelessdevices detected over time by the mobile device 102.

In some embodiments, the tracking system 100 identifies unauthorizedtracking devices tracking a user 103 based on communicating with one ormore community wireless devices 104 of other users 105. The communitywireless device 104 may provide detection even when the user 103 is notcarrying a mobile device 102, or carries the mobile device 102intermittently. For example, the user 103 can carry an authorizedtracking device, such as owner tracking device 610 or shared trackingdevice 612, for instance, coupled to the user's keys. Continuing withthis example, the user can also have an unauthorized tracking deviceattached to the user or an object that moves with the user. Even if theuser does not carry the mobile device 102, the tracking system 100communicates with one or more community mobile devices 104 of otherusers 105 to detect wireless signals from the authorized tracking deviceof the user 103, and wireless signals from the unauthorized trackingdevice. The tracking system 100 collects tracking data associated withboth tracking devices from community wireless devices 104, and detectsthe close proximity of the tracking devices in multiple locations atdifferent times, resulting in identification of the unauthorized device.The tracking system 100 may send a notification to the mobile device 102or other computing device of the user 103 when the unauthorized trackingdevice is detected. The tracking system 100 may remotely deactivate theunauthorized tracking device, or perform other remedial actions.

In some embodiments, a tracking device includes a network connection tothe tracking system 100. For example, the tracking device is anauthorized tracking device that moves with the user. Using techniques asdiscussed herein for the mobile device 102, the tracking device may beconfigured to scan and report tracking data of other wireless devices,including unknown devices which may be unauthorized tracking devices.Tracking devices may identify and remember one another (i.e. via a meshtopology), generate tracking data, and report the tracking data to thetracking system 100 via the network 108.

FIG. 8 illustrates a process 800 for identifying an unauthorizedtracking device, according to one embodiment. Method 800 may beperformed at 720 of method 700 to identify unauthorized tracking devicesfrom unknown wireless devices detected by the mobile device 102. Itshould be noted that although reference is made herein to theperformance of the process 800 by the tracking system 100, in someembodiments, the process can be performed by a mobile device or othersuitable device.

At 805, the tracking system 100 may be configured to identify an unknowndevice from a set of wireless devices detected by the mobile device 102.Identification of the unknown device may be performed by referencing alisting of known devices accessible to the tracking system 100. Knowndevices may include authorized devices and unauthorized devices.

Device authorization may be predefined, such as by referencing anauthorized device list and/or unauthorized device list. The known devicelist(s) may be stored and compared with received device IDs of detectedwireless devices to determine whether the wireless devices associatedwith the received device IDs are known devices. A wireless device thatfails to include a known device ID, may be determined as an unknowndevice. Various types of devices may be defined as authorized devices,such as owner tracking device 610, shared tracking device 612, orauthorized wireless device 614. The tracking system 100 may beconfigured to determine that a wireless device fails to be a knowndevice, and thus classifies the device as an unknown device.

In some embodiments, known devices may include shared tracking devices612 owned by other users. Such devices may be identified by on queryingan associated user (e.g., friend, connection, etc.) of the user 103 fromthe user database 210, identifying the owner tracking device of theassociated user, and determining that the owner tracking device of theassociated user is a shared tracking device 612 of the user 103.

At 810, the tracking system 100 may be configured to generate trackingdata based on communication signals between the unknown device and themobile device 102 over time. The tracking data represents the connectionbehavior of the unknown device with respect to the mobile device 102.The mobile device 102 may be configured to communicate with nearbywireless device over time (e.g., polling at time intervals). For eachwireless device, the tracking data may indicate a connection status overtime between the wireless device and the mobile device 102. Therefore,tracking data may be used to evaluate the characteristics or propertiesof communication signals, and used to determine whether the wirelessdevice is tracking the user. The tracking data may further includecommunication signal characteristics, such as signal strength, overtime.

At 815, the tracking system 100 may be configured to determine atracking device value for the unknown device based on the tracking data.The tracking device value refers to a measure of likelihood that theunknown device is behaving like a tracking device 106. The trackingdevice value may be used as criteria for triggering various unknowndevice handling tasks. These tasks may include sending warnings ornotifications to the mobile device 102 regarding an unknown device, andallowing the user to classify the unknown device as an authorized deviceor unauthorized device. In another example, a tracking device valueindicating a high likelihood of user tracking may trigger programmaticremedial actions, such as deactivation of the unauthorized trackingdevices by the tracking system 100.

In some embodiments, the tracking device value may be determined basedon the duration of connection between an unknown device and the mobiledevice 102. For example, an unknown device that has not been previouslydetected, but has followed the user for several minutes, may indicate ahigher likelihood that the unknown device is a tracking device. Anunknown device that maintains a connection for only a short period oftime, and with no subsequent connections for example, may indicate alower likelihood that the unknown device is a tracking device.

In some embodiments, the tracking device value may also be determinedbased on a location data of the mobile device 102. For example, aconnection that is maintained while the user is in motion may indicate ahigher likelihood that the unknown device is tracking the user (e.g.,the device is attached to the user, an object being transported by ortransporting the user, etc.). As a user moves around with an attachedunauthorized device, the probability that the unauthorized device isbeing used to track movement or the behavior of an object increases.

In some embodiments, the tracking device value may be determined basedon repeated or recurring connections between the unknown device and themobile device 102. If the unknown device and the mobile device 102connect at intermittent (e.g., daily, twice a day, etc.) or otherwise atrepeated times, this may indicate that the unknown device is a trackingdevice. For example, a tracking device may be planted on the user's car,and thus becomes detected by the mobile device 102 each time the user iswithin or near the car. Thus, an unknown device may be more likely to bea tracking device if there are recurring connections.

As discussed in the preceding examples, the tracking device value may bedetermined based on algorithmic transformations of the tracking data. Analgorithmic transformation maps or transforms the tracking data input toa tracking device value. In some embodiments, tracking device values maybe determined based on machine learning algorithm. For example, thealgorithmic transformation may be generated based on generating trainingsets (e.g., of ground truth input/output examples), and applying thetraining sets to a neural network to generate a trained neural networkmodel. The neural network model relates the tracking data input to anoutput tracking device value. A tracking device value for an unknowndevice may be determined based on applying input tracking data to thetrained neural network model, and receiving a tracking device value asan output.

In some embodiments, the tracking data of the unknown device isgenerated by one or more community mobile devices 104 of other users105. Here, the user 103 that is being tracked is not required to carrythe mobile phone 102 to receive unauthorized tracking device detectionservices from the tracking system 100. For example, the user carries anauthorized tracking device that is detected by community mobile devices104. If the user is also being tracked by an unauthorized trackingdevice, the community mobile devices 104 also detect the unauthorizedtracking device. The community mobile devices 104 generate tracking datarepresenting the connection behavior of the unknown device and anauthorized tracking device of the user 103. The tracking data iswirelessly detected by the one or more community mobile devices 104 ofother users 105. For example, different community mobile devices 104 maydetect wireless signals from both the unknown device and the authorizedtracking device of the user 103 over time, and at different locations.The tracking system 100 may be configured to determine a tracking devicevalue for the unknown device relative to the authorized tracking devicebased on the tracking data generated by the community mobile devices104. For example, tracking data that indicates the close proximity ofthe authorized tracking device and the unknown device at multiplelocations and at different times may indicate a higher likelihood thatthe unknown device is behaving like a tracking device with respect tothe user.

At 820, the tracking system 100 may be configured to determine atracking device warning threshold. The tracking device warning thresholddefines a minimum likelihood that an unknown device is a tracking devicefor the unknown device to be of further interest. Put another way,communication signals that fail to exceed the tracking device warningthreshold are sufficiently likely associated with non-tracking devices(e.g., wireless devices of others that happen to enter the communicationrange of the mobile device 102), and thus no user notification or othertracking device handling is required.

The tracking device warning threshold may define a minimum likelihoodthat a wireless device is a tracking device that is needed to initiatean alert to the user 103 regarding the wireless device. The alert mayallow the user to provide a classification for the unknown device asauthorized or unauthorized.

At 825, the tracking system 100 is configured to determine whether thetracking device value of the unauthorized device exceeds the trackingdevice warning threshold.

The tracking device warning threshold may be set at a low value toprovide more frequent warnings with higher probability of a falsepositive (e.g., a non-tracking device identified as tracking device). Incontrast, the tracking device warning threshold may be set at a highvalue to provide less frequent warnings, but with a higher possibilityof a false negative (e.g., a tracking device that fails to be identifiedas a tracking device until significant tracking activity has alreadyoccurred). In some embodiments, the tracking device warning thresholdmay correspond with the tracking data indicating that a wireless devicewas not previously detected, and then maintained a connection for atleast a predefined time (e.g., 10 minutes). As such, when tracking dataof a wireless device satisfies such characteristics, the tracking datacan be determined to exceed the device warning threshold.

In response to determining that the tracking device value fails toexceed the tracking device warning threshold, process 800 may return to810, where additional tracking data may be generated based oncommunication signals between the unknown device and the mobile device102. The additional tracking data may then be used to determine trackingdevice values, and so forth. Thus the tracking device value of awireless device is subject to update over time to facilitate continuousmonitoring for unknown devices.

Returning to 825, in response to determining that the tracking devicevalue exceeds the tracking device warning threshold, process 800 mayproceed to 830, where the tracking system 100 may be configured toprovide a notification regarding the unauthorized device to the mobiledevice.

The notification may include a message or other indication that theunknown device has been detected by the mobile device 102, and has beenflagged as a potential tracking device. The notification may include auser interface that facilitates user management of the unknown device.For example, the user interface may allow the user to classify theunknown device as an authorized device or unauthorized device. Themobile device 102 identifies the unknown device, and notifies the userof the mobile device of a presence of the unknown device.

The notification may further include various informational displays thatfacilitate user management for the unknown device. For example, thenotification may include a list of wireless devices connected with themobile device 102. The wireless devices may be identified based ondevice ID, device name, or other unique identifier. The list may includestatus indications for each wireless device indicating device statussuch as whether the wireless device is authorized, whether the device isa tracking device, and tracking device type (e.g., owner, shared,unauthorized, etc.). In some embodiments, the notification may furtherinclude a graph or other graphical representation of tracking data. Forexample, the graph may include tracking device values and/or connectionsignal strength as a function of time. Informational displays may alsobe provided to the display of the mobile device based on user request(e.g., even if no tracking device warning threshold has been exceeded).

At 835, the tracking system 100 may be configured to determine whetherthe user 103 authorizes the unknown device. The determination may bebased on a user generated message or user input provided in response tothe notification at 830. The mobile device 102 receives a confirmationfrom the user that the unknown device is an authorized or unauthorizeddevice. In response to receiving the confirmation from the user, themobile device 102 provides an indication that the unknown device is anauthorized or unauthorized device to the central tracking system 100,where it is classified accordingly.

In response to determining that the user 103 authorizes the unknowndevice, method 800 may proceed to 840, where the tracking system 100 maybe configured to classify the unknown device as an authorized device.For example, the device ID of the unknown device may be stored in anauthorized device list. As such, the authorized device is not identifiedas an unknown device at 805 for subsequent connections of the authorizeddevice with the mobile device 102.

Returning to 835, in response to determining that the user 103 does notauthorize the unknown device, or in response to an explicitclassification of the device as suspicious or unauthorized by the user,method 800 may proceed to 845, where the tracking system 100 may beconfigured to classify the unknown device as an unauthorized device. Forexample, the device ID of the unknown device may be stored in anunauthorized device list. As such, the unauthorized device is notidentified as an unknown device at 805 for subsequent connections of theunauthorized device with the mobile device 102.

At 840, the tracking system 100 may be configured to determine atracking device identification threshold for the unauthorized device.The tracking device identification threshold defines a minimum trackingdevice value needed to identify and classify a wireless device as atracking device. The tracking device identification threshold may be ahigher level threshold than the tracking device warning thresholddiscussed at 820. Put another way, tracking data for some devices may besufficiently characteristic of a tracking device to issue a usernotification (e.g., higher than minimum 10% likelihood threshold), butinsufficient to identify the device as being a tracking device withhigher level certainty (e.g., 50% likelihood or greater).

The tracking device identification threshold and tracking device warningthreshold are two examples of threshold values that may be applied totracking device values. In various embodiments, more or fewer thresholdvalues may be used. For example, a single threshold value may be usedthat triggers user notification, and identification as a trackingdevice. Here, unknown tracking devices may be identified from wirelessdevices within communication range of the mobile device. The user may benotified of presence of the unknown tracking device, and may classifythe unknown tracking device as being authorized or unauthorized asdiscussed above.

Each threshold value may be associated with different functionality andhandling, ranging from a low intervention for low threshold valuesatisfaction (e.g., warning a user) to a high intervention for highthreshold value satisfaction (e.g., deactivating a tracking device). Insome embodiments, the tracking device warning threshold and/or trackingdevice identification threshold may be set by the user.

At 855, the tracking system 100 may be configured to determine whetherthe tracking device value for the unauthorized device exceeds thetracking device identification threshold. For example, if a largertracking device value corresponds with a higher likelihood of being atracking device, then the tracking device value may be determined toexceed the tracking device identification threshold if the trackingdevice value exceeds the tracking device identification threshold.

In response to determining that the tracking device value fails toexceed the tracking device identification threshold, process 800 mayreturn to 810, where additional tracking data may be generated based oncommunication signals between the unauthorized device and the mobiledevice 102, and determine tracking device values based on thecommunication signals.

Returning to 855, in response to determining that the tracking devicevalue exceeds the tracking device identification threshold, process 800may proceed to 860, where the tracking system 100 may be configured toidentify and classify the unauthorized device as an unauthorizedtracking device. As such, tracking device values and thresholds may beused to identify tracking devices from the wireless devices that aredetected by the mobile device 102. In response to the unauthorizeddevice being identified as an unauthorized tracking device, variousremedial actions may be performed as discussed at 740-760 of process700.

Additional Considerations

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Any of the devices or systems described herein can be implemented by oneor more computing devices. A computing device can include a processor, amemory, a storage device, an I/O interface, and a communicationinterface, which may be communicatively coupled by way of communicationinfrastructure. Additional or alternative components may be used inother embodiments. In particular embodiments, a processor includeshardware for executing computer program instructions by retrieving theinstructions from an internal register, an internal cache, or othermemory or storage device, and decoding and executing them. The memorycan be used for storing data or instructions for execution by theprocessor. The memory can be any suitable storage mechanism, such asRAM, ROM, flash memory, solid state memory, and the like. The storagedevice can store data or computer instructions, and can include a harddisk drive, flash memory, an optical disc, or any other suitable storagedevice. The I/O interface allows a user to interact with the computingdevice, and can include a mouse, keypad, keyboard, touch screeninterface, and the like. The communication interface can includehardware, software, or a combination of both, and can provide one ormore interfaces for communication with other devices or entities.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a non-transitory, tangible computer readable storagemedium, or any type of media suitable for storing electronicinstructions, which may be coupled to a computer system bus.Furthermore, any computing systems referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

Embodiments of the invention may also relate to a product that isproduced by a computing process described herein. Such a product maycomprise information resulting from a computing process, where theinformation is stored on a non-transitory, tangible computer readablestorage medium and may include any embodiment of a computer programproduct or other data combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

1. A method for managing unauthorized tracking devices, comprising:receiving, by a tracking system, an indication that a wireless devicewithin a communication range of a mobile device has been identified asan unknown tracking device based on a tracking device value for thewireless device exceeding a tracking device warning threshold, thetracking device value being determined based on at least a duration of aconnection between the wireless device and the mobile device andindicating a likelihood that the wireless device is a tracking device;receiving, by the tracking system, a confirmation from the mobile devicethat the unknown tracking device is an unauthorized device; and inresponse to receiving the confirmation from the mobile device that theunknown tracking device is an unauthorized device, classifying, by thetracking system, the unknown tracking device as an unauthorized trackingdevice.
 2. The method of claim 1, further comprising providing, by thetracking system, an instruction for remotely deactivating theunauthorized tracking device to the mobile device.
 3. The method ofclaim 1, further comprising providing, by the tracking system, aninstruction for deactivating the unauthorized tracking device to theunauthorized tracking device.
 4. The method of claim 3, wherein theinstruction includes at least one of a security token, password, key orcode that is recognized by the unauthorized tracking device.
 5. Themethod of claim 3, wherein the instruction prevents the unauthorizedtracking device from wirelessly communicating with the mobile device. 6.The method of claim 3, wherein the instructions prevents theunauthorized tracking device from sharing location information withanother device.
 7. The method of claim 1, further comprising providing,by the tracking system, an instruction for deactivating the unauthorizedtracking device to another mobile device associated with theunauthorized tracking device.
 8. The method of claim 1, furthercomprising, by the tracking system: receiving a device identifier of theunauthorized tracking device; and determining the unauthorized trackingdevice is a managed tracking device based on comparing the deviceidentifier with a managed tracking device list.
 9. The method of claim1, further comprising, by the tracking system, in response to receivingthe confirmation from the mobile device that the unknown tracking deviceis an unauthorized device, disassociating the unknown tracking devicewith a user profile of an owner of the unknown tracking device.
 10. Themethod of claim 1, wherein the connection between the wireless deviceand the mobile device includes a Bluetooth wireless network.
 11. Atracking system for managing unauthorized tracking devices, comprising:a server configured to: receive an indication that a wireless devicewithin a communication range of a mobile device has been identified asan unknown tracking device based a tracking device value for thewireless device exceeding a tracking device warning threshold, thetracking device value being determined based on at least on a durationof a connection between the wireless device and the mobile device andindicating a likelihood that the wireless device is a tracking device;receiving a confirmation from the mobile device that the unknowntracking device is an unauthorized device; and in response to receivingthe confirmation from the mobile device that the unknown tracking deviceis an unauthorized device, classifying the unknown tracking device as anunauthorized tracking device.
 12. The system of claim 11, wherein theserver is further configured to provide an instruction for remotelydeactivating the unauthorized tracking device to the mobile device. 13.The system of claim 11, wherein the server is further configured toprovide an instruction for deactivating the unauthorized tracking deviceto the unauthorized tracking device
 14. The system of claim 13, whereinthe instruction includes at least one of a security token, password, keyor code that is recognized by the unauthorized tracking device.
 15. Thesystem of claim 13, wherein the instruction prevents the unauthorizedtracking device from wirelessly communicating with the mobile device.16. The system of claim 13, wherein the instructions prevents theunauthorized tracking device from sharing location information withanother device.
 17. The system of claim 11, wherein the server isfurther configured to provide an instruction for deactivating theunauthorized tracking device to another mobile device associated withthe unauthorized tracking device.
 18. The system of claim 11, whereinthe server is further configured to: receive a device identifier of theunauthorized tracking device; and determine the unauthorized trackingdevice is a managed tracking device based on comparing the deviceidentifier with a managed tracking device list.
 19. The system of claim11, wherein the server is further configured to, in response toreceiving the confirmation from the mobile device that the unknowntracking device is an unauthorized device, disassociate the unknowntracking device with a user profile of an owner of the unknown trackingdevice.
 20. The system of claim 11, wherein the connection between thewireless device and the mobile device includes a Bluetooth wirelessnetwork.